Skip to content

Add a skill for the weekly product updates#552

Merged
danbarr merged 12 commits intomainfrom
weekly-skill
Feb 18, 2026
Merged

Add a skill for the weekly product updates#552
danbarr merged 12 commits intomainfrom
weekly-skill

Conversation

@rdimitrov
Copy link
Member

@rdimitrov rdimitrov commented Feb 13, 2026

Description

The following PR adds a skill for the weekly product updates (applied the feedback to look only at the PRs included in the release changelogs)

Type of change

  • Other: internal tooling

Submitter checklist

Content and formatting

  • I have reviewed the content for technical accuracy
  • I have reviewed the content for spelling, grammar, and style

Reviewer checklist

Content

  • I have reviewed the content for technical accuracy
  • I have reviewed the content for spelling, grammar, and style

Copilot AI review requested due to automatic review settings February 13, 2026 23:28
@vercel
Copy link

vercel bot commented Feb 13, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs-website Ready Ready Preview, Comment Feb 17, 2026 11:08pm

Request Review

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a comprehensive Claude skill for generating weekly product updates by analyzing GitHub releases and transforming technical changes into marketing-ready content. The skill provides detailed guidance on terminology, workflow steps, output formatting, and content guidelines to ensure consistent, benefit-focused updates for the ToolHive project.

Changes:

  • Added .claude/skills/weekly-product-updates/SKILL.md with complete workflow for generating weekly product updates from GitHub releases
  • Includes repository mapping, date range handling, PR filtering logic, and two output formats (summary and blog)
  • Provides comprehensive content guidelines covering tone, structure, and common pitfalls

Comment on lines 55 to 64
```bash
if [ -z "$ARGUMENTS" ] || [ "$ARGUMENTS" = "last-week" ]; then
END_DATE=$(date +%Y-%m-%d)
START_DATE=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)
else
START_DATE=$(echo "$ARGUMENTS" | cut -d'.' -f1)
END_DATE=$(echo "$ARGUMENTS" | cut -d'.' -f3)
fi
echo "Analyzing: $START_DATE to $END_DATE"
```
Copy link

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The bash script examples use variables like $ARGUMENTS, $START_DATE, and $END_DATE without proper quoting in some places. While this is example code, it's good practice to quote variables to prevent word splitting and globbing issues. Consider adding quotes around variable expansions, e.g., "$ARGUMENTS", especially when the values could contain spaces or special characters.

Copilot uses AI. Check for mistakes.
Comment on lines 56 to 62
if [ -z "$ARGUMENTS" ] || [ "$ARGUMENTS" = "last-week" ]; then
END_DATE=$(date +%Y-%m-%d)
START_DATE=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)
else
START_DATE=$(echo "$ARGUMENTS" | cut -d'.' -f1)
END_DATE=$(echo "$ARGUMENTS" | cut -d'.' -f3)
fi
Copy link

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The argument parsing logic is described (line 26) but the bash script example (lines 55-64) doesn't show how to extract the format argument (summary or blog) from $ARGUMENTS. Consider adding an example showing how to parse both the format and date range from the arguments, e.g., checking if the first word is 'blog' or 'summary' and then extracting the remaining arguments as the date range.

Suggested change
if [ -z "$ARGUMENTS" ] || [ "$ARGUMENTS" = "last-week" ]; then
END_DATE=$(date +%Y-%m-%d)
START_DATE=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)
else
START_DATE=$(echo "$ARGUMENTS" | cut -d'.' -f1)
END_DATE=$(echo "$ARGUMENTS" | cut -d'.' -f3)
fi
# Default format and date range
FORMAT="summary"
DATE_RANGE="$ARGUMENTS"
# If the first word is "summary" or "blog", treat it as the format
if [ -n "$ARGUMENTS" ]; then
FIRST_WORD="${ARGUMENTS%% *}"
if [ "$FIRST_WORD" = "summary" ] || [ "$FIRST_WORD" = "blog" ]; then
FORMAT="$FIRST_WORD"
# Remove the first word and leading space to get the date range (if any)
DATE_RANGE="${ARGUMENTS#"$FIRST_WORD"}"
DATE_RANGE="${DATE_RANGE# }"
fi
fi
# Determine the actual dates from the date range
if [ -z "$DATE_RANGE" ] || [ "$DATE_RANGE" = "last-week" ]; then
END_DATE=$(date +%Y-%m-%d)
START_DATE=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)
else
START_DATE=$(echo "$DATE_RANGE" | cut -d'.' -f1)
END_DATE=$(echo "$DATE_RANGE" | cut -d'.' -f3)
fi
echo "Format: $FORMAT"

Copilot uses AI. Check for mistakes.

[Opening paragraph: 2-3 sentences setting the theme, hinting at value without feature-listing, accessible to both open source and commercial audiences.]

{/_ truncate _/}
Copy link

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The truncate comment syntax uses underscores instead of asterisks to avoid being interpreted as a comment in this markdown file. However, when Claude generates the actual blog post, it needs to output the correct syntax with asterisks: {/* truncate */}. Consider adding a clarifying note that the underscores should be replaced with asterisks in the actual output.

Copilot uses AI. Check for mistakes.
rdimitrov and others added 11 commits February 18, 2026 00:17
Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Dan Barr <danbarr@users.noreply.github.com>
Co-authored-by: Dan Barr <danbarr@users.noreply.github.com>
Co-authored-by: Dan Barr <danbarr@users.noreply.github.com>
Co-authored-by: Dan Barr <danbarr@users.noreply.github.com>
Co-authored-by: Dan Barr <danbarr@users.noreply.github.com>
Co-authored-by: Dan Barr <danbarr@users.noreply.github.com>
Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
@danbarr danbarr merged commit 32b00cb into main Feb 18, 2026
10 checks passed
@danbarr danbarr deleted the weekly-skill branch February 18, 2026 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments